# Page Not Found

The URL `Note input/Entering notes and rests` does not exist. This page may have been moved, renamed, or deleted.

## Suggested Pages

You may be looking for one of the following:
- [Entering notes and rests](https://handbook.musescore.org/basics/entering-notes-and-rests.md)
- [Editing notes and rests](https://handbook.musescore.org/basics/editing-notes-and-rests.md)
- [Entering and editing text](https://handbook.musescore.org/text/entering-and-editing-text.md)
- [Instruments, staves, and systems](https://handbook.musescore.org/notation/instruments-staves-and-systems.md)
- [Tremolos and rolls](https://handbook.musescore.org/notation/expressive-markings/tremolos-and-rolls.md)

## How to find the correct page

If the exact page cannot be found, you can still retrieve the information using the documentation query interface.

### Option 1 — Ask a question (recommended)

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://handbook.musescore.org/basics/entering-notes-and-rests.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

### Option 2 — Browse the documentation index

Full index: https://handbook.musescore.org/sitemap.md

Use this to discover valid page paths or navigate the documentation structure.

### Option 3 — Retrieve the full documentation corpus

Full export: https://handbook.musescore.org/llms-full.txt

Use this to access all content at once and perform your own parsing or retrieval. It will be more expensive.

## Tips for requesting documentation

Prefer `.md` URLs for structured content, append `.md` to URLs (e.g., `/basics/entering-notes-and-rests.md`).

You may also use `Accept: text/markdown` header for content negotiation.